 |
|
The penalty to be paid for all this seemingly good stuff in
terms of reliability is performance. The acknowledgments, buffering,
and retransmission that happen within the X.25 protocols add latency
(especially if there are many hops between source and destination),
meaning this protocol provides poor performance for carrying TCP
traffic that already handles these functions. If your main interest
is in networking TCP/IP protocols and transporting legacy protocols
such as IPX, SNA, or NetBIOS over a TCP/IP network, it is unlikely
you will deploy X.25. In such situations, X.25 is really a competing
technology to TCP/IP. Bearing this in mind, in the example
configurations, we will only look at how two IP nodes can
communicate across an X.25 network via encapsulation of IP data
within an X.25 frame for transmission over an X.25 network (termed
tunneling). We'll also examine how to translate X.25 traffic to IP, so
that a host using TCP/IP communications can communicate with an X.25
host. |
| |